Performing Application-Specific Searches Using Touchscreen-Enabled Computing Devices

ABSTRACT

Systems and methods are provided and include receiving, at a touchscreen of a user device, a user input from a user of the user device, the user input selecting an application (app) icon displayed at the touchscreen. The user device receives a search query from the user. In response to receiving the user input and the search query, the user device generates search results based on the search query, each search result specifying a state of a native app associated with the app icon. The user device displays the search results to the user.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/221,767, filed on Sep. 22, 2015. The entire disclosure of theapplication referenced above is incorporated herein by reference.

TECHNICAL FIELD

This disclosure generally relates to the field of search, and moreparticularly to techniques for performing searches usingtouchscreen-enabled computing devices.

BACKGROUND

In recent years, the use of computers, tablets, smartphones, smartwatches, and other stationary and mobile computing devices has grownsignificantly. Additionally, the inclusion of various touchscreendevices configured to receive user inputs at display screens of theseand other computing devices has also increased. Today, many consumer andindustrial computing devices and appliances are capable of receivinguser inputs at display screens via a variety of different touchscreentechnologies, including resistive, capacitive, surface-acoustic-wave(SAW), optical, and other touchscreen types.

Moreover, the number of software applications (apps) available for theseand other devices has also grown. Today, many diverse software apps canbe accessed on various computing devices. The software apps includebusiness driven apps, games, educational apps, news apps, shopping apps,messaging apps, media streaming apps, and social networking apps, assome examples. Because of the large number of software apps availabletoday and the wide range of functionality they provide, computing deviceusers often require the ability to search for and access specificsoftware app functionality.

SUMMARY

In one example, a method includes receiving, at a touchscreen of a userdevice, a user input from a user of the user device. In this example,the user input selects an application (app) icon displayed at thetouchscreen. The method further includes receiving, at the user device,a search query from the user. The method still further includes, inresponse to receiving the user input and the search query, generating,using the user device, search results based on the search query. In thisexample, each search result specifies a state of a native app associatedwith the app icon. The method also includes displaying, using the userdevice, the search results to the user.

In other features, the user input can comprise one or more of a fingercontact input and a pressure input with respect to the touchscreen.

In other features, the user input can comprise a momentary user input.

In other features, the user input can comprise a prolonged user inputhaving a time duration that is longer than a momentary user input.

In other features, the user input can comprise a predetermined usergesture with respect to the touchscreen.

In other features, receiving the user input and the search query fromthe user can comprise receiving the search query while receiving theuser input.

In other features, receiving the user input and the search query fromthe user can comprise receiving the search query following receiving theuser input.

In other features, receiving the search query from the user can comprisereceiving the search query via voice input.

In other features, receiving the search query from the user can comprisereceiving the search query via text input.

In other features, receiving the search query from the user can compriseproviding, using the user device, a user prompt to the user and inresponse to providing the user prompt, receiving the search query fromthe user.

In other features, providing the user prompt to the can compriseproviding one or more of the following to the user: a visual output atthe touchscreen; a sound output; a voice command output; and a vibrationoutput.

In other features, generating the search results in response toreceiving the user input and the search query can comprise determining,using the user device, a storage location included on the user deviceand corresponding to the native app associated with the app icon,performing, using the user device, a search of the storage locationusing the search query, and generating, using the user device, thesearch results based on performing the search.

In other features, generating the search results in response toreceiving the user input and the search query can comprise determining,using the user device, an app programming interface (API) correspondingto the native app associated with the app icon, querying, using the userdevice, the API using the search query, and receiving, at the userdevice, the search results from the API in response to querying the API.

In other features, generating the search results in response toreceiving the user input and the search query can comprisestransmitting, using the user device, the search query to a search systemconfigured to generate search results in response to a received searchquery and receiving, at the user device, the search results from thesearch system in response to transmitting the search query.

In other features, the method can further comprise transmitting, usingthe user device, an indication of the native app associated with the appicon to the search system, wherein receiving the search results from thesearch system comprises receiving the search results in response totransmitting the indication.

In other features, generating the search results in response toreceiving the user input and the search query can comprise launching,using the user device, the native app associated with the app icon, andproviding, using the user device, one or more commands to the launchednative app, the one or more commands configured to cause the native appto generate the search results.

In other features, the search results can include one or more app accessmechanisms (AAMs), wherein each AAM references the native app associatedwith the app icon and indicates one or more operations for the nativeapp to perform, and wherein the native app performing the one or moreoperations sets the native app into one of the one or more states withinthe native app.

In other features, displaying the search results to the user cancomprise displaying the search results at the touchscreen as one or moreuser selectable links.

In other features, displaying the search results to the user cancomprise forwarding the search results for display as one or more userselectable links to a computing device other than the user device.

In other features, displaying the search results to the user cancomprise launching, using the user device, the native app associatedwith the app icon and displaying, using a graphical user interface (GUI)of the launched native app, the search results to the user as one ormore user selectable links.

In another example, a system includes one or more computing devicesconfigured to receive, at a touchscreen of a user device, a user inputfrom a user of the user device. In this example, the user input selectsan app icon displayed at the touchscreen. The one or more computingdevices are further configured to receive, at the user device, a searchquery from the user. The one or more computing devices are still furtherconfigured to, in response to receiving the user input and the searchquery, generate, using the user device, search results based on thesearch query. In this example, each search result specifies a state of anative app associated with the app icon. The one or more computingdevices are also configured to display, using the user device, thesearch results to the user.

In another example, a non-transitory computer-readable storage mediumincludes instructions that cause one or more computing devices toreceive, at a touchscreen of a user device, a user input from a user ofthe user device. In this example, the user input selects an app icondisplayed at the touchscreen. The instructions further cause the one ormore computing devices to receive, at the user device, a search queryfrom the user. The instructions still further cause the one or morecomputing devices to, in response to receiving the user input and thesearch query, generate, using the user device, search results based onthe search query. In this example, each search result specifies a stateof a native app associated with the app icon. The instructions alsocause the one or more computing devices to display, using the userdevice, the search results to the user.

In another example, a computing device comprises a touchscreenconfigured to display an application (app) icon and receive a user inputfrom a user of the computing device, an input/output componentconfigured to receive a search query from the user, one or more memorycomponents configured to store computer-readable instructions, and oneor more processing units configured to execute the computer-readableinstructions. The computer-readable instructions, when executed by theone or more processing units, cause the one or more processing units toreceive the user input from the user at the touchscreen, the user inputselecting the app icon displayed at the touchscreen, receive the searchquery from the user using the input/output component, in response toreceiving the user input and the search query, generate one or moresearch results based on the search query, each search result specifyinga state of a native app associated with the app icon, and display theone or more search results to the user.

The details of one or more implementations of the disclosure are setforth in the accompanying drawings and the description below. Otheraspects, features, and advantages will be apparent from the descriptionand drawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1B illustrate example user devices that may be used toimplement the techniques of the present disclosure.

FIGS. 2A-2B are functional block diagrams of an example user device incommunication with one or more of a user, an application programminginterface (API), and a search system.

FIGS. 3A-4F illustrate example graphical user interfaces (GUIs) that maybe generated on a user device according to this disclosure.

FIGS. 5A-5D are flow diagrams that illustrate example methods forgenerating search results at a user device based on a user input and asearch query received from a user.

FIG. 5E is a flow diagram that illustrates an example method forperforming one or more actions in response to a user selecting a searchresult on a user device.

FIG. 6 illustrates an example environment that includes a user deviceand a search system that communicate via a network.

FIG. 7 is a functional block diagram of an example search system.

FIG. 8 is a functional block diagram of an example search module.

FIGS. 9A-9B illustrate example application state records of a searchdata store.

FIG. 10 is a flow diagram that illustrates an example method forperforming a search for application state records based on a searchquery received from a user device.

DETAILED DESCRIPTION

The figures and the following description relate to exampleimplementations by way of illustration only. It should be noted thatfrom the following discussion, alternative implementations of thestructures and methods disclosed herein will be readily recognized asviable alternatives that may be employed without departing from thescope of this disclosure.

The present disclosure generally relates to the field of search, and,more particularly, to techniques for performing searches for states ofnative apps using computing devices equipped with touchscreen-enableddisplay screens (e.g., laptops, tablets, smartphones, and smartwatches). Specifically, the techniques of this disclosure are directedto computing devices configured to receive user inputs, including one ormore of finger contact inputs and pressure inputs, from users viadisplay screens capable of detecting (e.g., sensing) the inputs. Forexample, to receive the pressure inputs, the display screens may includeresistive touchscreens, push-button-based touchscreens, or otherpressure-sensitive sensors or input devices. Additionally, oralternatively, to receive the finger contact inputs, the display screensmay include capacitive touchscreens or other finger contact-sensitivesensors or input devices.

According to the techniques disclosed herein, a user device (e.g., asmartphone or a smart watch) may receive a user input from a user at atouchscreen of the device. For example, the user input may include oneor more of a finger contact input and a pressure input received from theuser at the touchscreen. In this example, the user input may select anapp icon displayed at the touchscreen (e.g., select an area of a displayscreen of the user device, which includes a touchscreen, used to displaythe icon). For example, the app icon may be associated with a native appthat is installed on the user device. The user device may furtherreceive a search query from the user (e.g., during or followingreceiving the user input from the user). For example, the user devicemay receive the search query using any of a voice input and a text inputby the user. In some examples, to receive the search query, the userdevice may first provide a user prompt (e.g., a visual, audible, and/orhaptic output) to the user. In these examples, the user prompt may beconfigured to cause the user to provide the search query to the userdevice.

In response to receiving the user input and search query from the user,the user device may generate one or more search results based on thesearch query. In this example, each search result may both be responsiveto the search query and specify a state of a native app that isassociated with the app icon selected by the user input. In someexamples, the user device may generate the search results locally (e.g.,by performing a search of a local storage location used by the nativeapp using the search query). In other examples, the user device maygenerate the search results by querying an API associated with thenative app using the search query and receiving the results in responseto querying the API. In still other examples, the user device maygenerate the search results by transmitting the search query to a searchsystem and receiving the results in response to transmitting the query.In some examples, to generate the search results, the user device maylaunch the native app and generate the results using (e.g., within) thelaunched app. The user device may then display the search results to theuser, e.g., as one or more user selectable links. As one example, theuser device may display the search results as the user selectable linksat a display screen (e.g., that includes the touchscreen) of the device.For example, the user device may launch the native app and display thesearch results using (e.g., within) the launched app. As anotherexample, the user device may forward the search results for display asthe user selectable links to another (e.g., nearby) computing device.

In this manner, the techniques described herein may improve the wayusers interact with computing devices that include touchscreen-enableddisplay screens to perform searches for states of native apps.Specifically, the techniques may enable a user of a user device toperform a search for states of a native app that is installed on thedevice by interacting directly with an app icon associated with the appand displayed at a touchscreen of the device. As a result, thetechniques may enable the user to avoid the inconvenience of firstlaunching the native app on the user device, and subsequently performingthe search for the states within the launched app. Using the techniquesdescribed herein may, in some examples, improve the user's experiencewhen performing the search for the states of the native app using theuser device.

FIGS. 1A-1B illustrate example user devices 100 that may be used toimplement the techniques of the present disclosure. As shown in FIG. 1A,the user device 100 may be a smart watch computing device configured tobe worn around a user's wrist. Alternatively, as shown in FIG. 1B, theuser device 100 may be a smartphone computing device configured to beheld in a user's palm. In other examples, the user device 100 may be atablet, a laptop computer, or a desktop computer. In still otherexamples, the user device 100 may be a computing device having anotherform factor, such as a computing device included in a vehicle, a gamingdevice, a television, or another appliance (e.g., a networked homeautomation device or appliance).

In general, the user device 100 of this disclosure may be any computingdevice that includes a touchscreen 102 (e.g., a user input devicelayered over a display screen and configured to receive finger contactand/or pressure inputs from a user). The touchscreen 102 may beconfigured to receive user inputs from users of the user device 100, asdescribed herein. For example, the touchscreen 102 may be configured toreceive finger contact inputs from the users (e.g., the touchscreen 102may be a capacitive touchscreen configured to detect user fingercontacts, such as user finger taps and swipes). For instance, thetouchscreen 102 may be configured to receive user inputs generated usingany of fingers of the users' hands, other parts of the users' bodies(e.g., portions of the users' palms), and other objects that are notpart of the users' bodies (e.g., conductive styli), so long as the bodyparts or objects used are substantially electrically conductive.Additionally, or alternatively, the touchscreen 102 may be configured toreceive pressure inputs from the users (e.g., the touchscreen 102 may bea resistive touchscreen configured to detect user pressure inputs, suchas user finger or stylus pushes and swipes). For example, thetouchscreen 102 may be configured to receive user inputs generated usingany of fingers of the users' hands, other parts of the users' bodies,and other objects not part of the users' bodies (e.g., styli),irrespective of the body part or object being electrically conductive.

The user device 100 may also be any computing device that is capable ofreceiving search queries from the users, as also described herein. Forexample, the user device 100 may be configured to receive the searchqueries from the users via voice input (e.g., using one or moremicrophone devices, such as a mic array, associated electricalcircuitry, and speech recognition software included on the device 100).

Additionally, or alternatively, the user device 100 may be configured toreceive the search queries from the users via text input (e.g., using avirtual keyboard displayed at the touchscreen 102 or a dedicated keypadincluded on the device 100).

The user device 100 may also be any computing device that is capable ofgenerating and displaying search results that are responsive to thesearch queries received from the users and specifying states ofparticular native apps, as further described herein. As one example, togenerate the search results, the user device 100 may be configured toperform searches of local storage locations associated with native appsthat are installed on the device 100 using the search queries. Asanother example, to generate the search results, the user device 100 maybe configured to query APIs corresponding to native apps that areinstalled on the device 100 using the search queries. As still anotherexample, to generate the search results, the user device 100 may beconfigured to transmit the search queries to a search system and receivethe results from the system in response to transmitting the queries. Theuser device 100 may be configured to display the search results to theusers (e.g., at a display screen including the touchscreen 102 of thedevice 100, or by forwarding the results for display at anothercomputing device).

The user device 100 may use various different operating systems orplatforms. In examples where the user device 100 is a mobile device(e.g., a smart watch or a smartphone), the device 100 may operate usingan operating system (OS) such as ANDROID® by Google, Inc., 10S® byApple, Inc., or WINDOWS PHONE® by Microsoft Corporation. In exampleswhere the user device 100 is a laptop or desktop computer, the device100 may use an OS such as MICROSOFT WINDOWS® by Microsoft Corporation,MAC OS® by Apple, Inc., or LINUX® (LINUX® is the registered trademark ofLinus Torvalds in the U.S. and other countries). The user device 100 mayinteract with users and/or other devices or systems using operatingsystems other than those described herein, whether presently availableor developed in the future.

FIGS. 2A and 2B are functional block diagrams of an example user device100 in communication with one or more users 226, one or more native appprogramming interfaces (APIs) 232, and/or a search system 104. As shownin FIG. 2A, the user device 100 includes one or more processing units200, memory component(s) 202, input/output (I/O) components 204, andinterconnect components 206. The I/O components 204 may include one ormore transceivers 207. As further shown in FIG. 2A, the memorycomponent(s) 202, for example, store code that is executed by theprocessing unit(s) 200 for an operating system (OS) 208, a web browserapplication 210, one or more native applications 212 (e.g., that areinstalled on the user device 100), and a search application 214. Forexample, the processing unit(s) 200 may be configured to executeinstructions stored in the memory component(s) 202 and communicate withthe memory component(s) 202 and I/O component(s) 204, including thetransceiver(s) 207 (e.g., via the interconnect component(s) 206). Eachof the OS 208, web browser app 210, native app(s) 212, and search app214 may be embodied in computer-executable instructions that areexecuted by the processing unit(s) 200. The memory component(s) 202 maybe configured to store executable instructions, system parameters, andother data in addition to the contents described above.

As shown in FIG. 2B, the user device 100 includes a touchscreen inputmodule 216, a voice input module 218, and an application/query searchmodule 220. As also shown, the touchscreen input module 216 includes afinger contact input detection module 222 and a pressure input detectionmodule 224. The modules may be implemented by and embodied in electronichardware, software, firmware, and/or any combination thereof. Forexample, one or more of the touchscreen input module 216, the fingercontact input detection module 222, the pressure input detection module224, the voice input module 218, and the app/query search module 220 maybe implemented by and embodied in computer-executable instructionsstored in the memory component(s) 202 that are executed by theprocessing unit(s) 200. Alternatively, one or more of the touchscreeninput module 216, the finger contact input detection module 222, thepressure input detection module 224, the voice input module 218, and theapp/query search module 220 may be, in whole or in part, implemented byand embodied in hardware that is separate from, but in communicationwith, the processing unit(s) 200, the memory component(s), and the I/Ocomponent(s) 204, including the transceiver(s) 207, via the interconnectcomponent(s) 206.

With reference to FIG. 2A, each of the I/O component(s) 204 may beconfigured to (e.g., at the direction of the processing unit(s) 200)receive inputs to the user device 100 and transmit outputs from thedevice 100. In addition, the transceiver(s) 207 may be configured to(e.g., at the direction of the processing unit(s) 200) transmit data toand receive data from other devices in communication with the userdevice 100. The interconnect component(s) 204 (e.g., a bus) may beconfigured to provide communication between the processing unit(s) 200,memory component(s) 202, the I/O component(s) 204 (including thetransceiver(s) 207), and other systems or devices included in and/oroutside the user device 100.

The units, components, and modules of the user device 100 describedabove may enable the device 100 to perform the techniques attributed tothe device 100 in this disclosure. For example, the user device 100(e.g., the processing unit(s) 200 executing instructions stored in thememory component(s) 202) may be configured to receive (e.g., via the I/Ocomponent(s) 204) user inputs 228 from users 226 of the device 100 at atouchscreen 102 of the device 100. In this example, the user inputs 228may select app icons displayed at the touchscreen 102. In some examples,the user device 100 (e.g., the processing unit(s) 200 executinginstructions stored in the memory component(s) 202) may be configured toprovide (e.g., via the I/O component(s) 204) user prompts (e.g., visual,audible, and/or haptic outputs) to the users 226. In these examples, theuser prompts may be configured to prompt the users 226 to provide searchqueries 230 to the user device 100. The user device 100 may furtherreceive (e.g., via the I/O component(s) 204) the search queries 230 fromthe users 226 (e.g., in response to providing the user prompts). Theuser device 100 (e.g., the processing unit(s) 200 executing instructionsstored in the memory component(s) 202) may also be configured to, inresponse to receiving the user inputs 228 and search queries 230,generate, based on the search queries 230, search results 234 that areresponsive to the queries 230 and specify states of native apps that areassociated with the app icons selected by the inputs 228. Lastly, theuser device 100 may display (e.g., via the I/O component(s) 204) thesearch results 234 to the users 226 (e.g., as user selectable links).

To perform one or more of receiving the user inputs 228, providing theuser prompts, receiving the search queries 230, generating the searchresults 234, and displaying the results 234, the processing unit(s) 200may execute one or more instructions included in the memory component(s)202. For example, the processing unit(s) 200 may execute instructionsassociated with one or more of the OS 208, web browser app 210, nativeapp(s) 212, search app 214, touchscreen input module 216, voice inputmodule 218, app/query search module 220, finger contact input detectionmodule 222, and pressure input detection module 224. In a specificexample, the processing unit(s) 200 may execute instructions that causethe user device 100 to run the OS 208. To receive the user inputs 228from the user(s) 226, the processing unit(s) 200 may executeinstructions that cause the user device 100 to run one or more of thefinger contact input detection module 222 and pressure input detectionmodule 224 of the touchscreen input module 216, e.g., within the OS 208.For example, to receive finger contact inputs (e.g., taps) from theuser(s) 226 (e.g., in cases where the touchscreen 102 includes acapacitive touchscreen), the processing unit(s) 200 may executeinstructions that cause the user device 100 to run the finger contactinput detection module 222. Additionally, to receive pressure inputs(e.g., pushes) from the user(s) 226 (e.g., in cases where thetouchscreen 102 includes a resistive touchscreen), the processingunit(s) 200 may execute instructions that cause the user device 100 torun the pressure input detection module 224. In general, the touchscreeninput module 216, including the finger contact input detection module222 and pressure input detection module 224, may be one or morededicated software modules configured to receive user inputs 228 (e.g.,finger contact and/or pressure inputs) from the user(s) 226 at thetouchscreen 102 of the user device 100.

In some examples, to provide the user prompts to the user(s) 226, theprocessing unit(s) 200 may execute instructions that cause the userdevice 100 to run one or more of the web browser app 210, native app(s)212, and search app 214, e.g., within the OS 208. In other examples, toprovide the user prompts to the user(s) 226, the processing unit(s) 200may execute instructions that cause the user device 100 to run a soundand/or vibration output module (not shown). In general, to provide theuser prompts, the user device 100 may run one or more of a web-basedapp, a native app, and a dedicated software module configured togenerate visual, audible, and/or haptic outputs to the user of the userdevice 100, as described herein.

To receive the search queries 230 from the user(s) 226, the processingunit(s) 200 may further execute instructions that cause the user device100 to run one or more of the voice input module 218, web browser app210, native app(s) 212, and search app 214, e.g., within the OS 208. Insome examples, to receive the search queries 230, the processing unit(s)200 may execute instructions that cause the user device 100 to run thevoice input module 218 (e.g., in cases where the user device 100receives the queries 230 from the user(s) 226 via voice input).Alternatively, to receive the search queries 230, the processing unit(s)200 may execute instructions that cause the user device 100 to run anyof the web browser app 210, native app(s) 212, search app 214, andanother module (not shown) (e.g., in cases where the user device 100receives the queries 230 from the user(s) 226 via text input). Ingeneral, to receive the search queries 230, the user device 100 may runone or more of a web-based app, a native app, and a dedicated softwaremodule configured to receive voice or text inputs (e.g., via a textinput field and a virtual keyboard or dedicated keypad) from the user ofthe device 100, as described herein.

To generate the search results 234 in response to receiving the userinputs 228 and search queries 230, the processing unit(s) 200 mayexecute instructions that cause the user device 100 to run the app/querysearch module 220. As one example, the app/query search module 220 maycause the user device 100 to determine a storage (e.g., memory) locationincluded on the device 100. In this example, the storage location maycorrespond to (e.g., be used by) a native app associated with an appicon that has been selected by a user input 228, as described herein.The app/query search module 220 may then cause the user device 100 toperform a search of the storage location using the search query 230 andgenerate the search results 234 based on performing the search. Asanother example, the app/query search module 220 may cause the userdevice 100 to determine an API that corresponds to (e.g., includes dataused by) the native app associated with the selected app icon. Theapp/query search module 220 may then cause the user device 100 to querythe API using the search query 230 and receive the search results 234from the API in response to querying the API. As still another example,the app/query search module 220 may cause the user device 100 totransmit the search query 230 to a search system 104 configured togenerate search results in response to a received search query andreceive the search results 234 from the system 104 in response totransmitting the query 230.

To display the search results 234 to the user(s) 226, the processingunit(s) 200 may execute instructions that cause the user device 100 torun one or more modules (not shown) that cause the device 100 to performany of a variety of actions. As one example, the user device 100 may runa module (not shown) that generates user selectable links for the searchresults 234 and displays the links to the user(s) 226. For example, theuser device 100 may first launch a native app associated with an appicon that has been selected by a user input 228. The user device 100 maythen display the search results as the user selectable links within aGUI of the launched native app. As another example, the user device 100may run a module that forwards the search results 234 (e.g., via awireless and/or wired communication network) to one or more other (e.g.,proximate) computing devices for display as the user selectable links.

FIGS. 3A-4F illustrate example GUIs that may be generated on a userdevice 100 according to this disclosure. The user device 100 shown inFIGS. 3A-4F is one of a smartphone computing device and a wrist watchcomputing device (e.g., a smart watch). Example smartphone computingdevices include the SAMSUNG S® devices developed by Samsung ElectronicsCo., Ltd. and the APPLE IPHONE® devices developed by Apple Inc. Examplewrist watch computing devices include the SAMSUNG GALAXY GEAR®, SAMSUNGGALAXY GEAR® 2, SAMSUNG GEAR® 2 Neo, and SAMSUNG GEAR FIT® developed bySamsung Electronics Co., Ltd., as well as the APPLE WATCH® developed byApple Inc.

As shown in FIG. 3A, initially, the user device 100 (e.g., a smartphonecomputing device) receives a user input 228 from a user 226 of thedevice 100 at a touchscreen 102 of the device 100. As also shown, theuser input 228 indicates a selection of an app icon that is displayed atthe touchscreen 102. As described herein, the app icon may be associatedwith a native app (e.g., one of the native app(s) 212) that is installedon the user device 100. In the example of FIGS. 3A-3B, the native appassociated with the selected app icon corresponds to “TripAdvisor@” byTripAdvisor, LLC (hereinafter, “TripAdvisor”). In this example, the userdevice 100 further receives a search query 230 of “RESTAURANTS INCHICAGO” 230 from the user 226 via voice input. In other examples, theuser device 100 may receive the search query 230 from the user 226 viatext input, as described below with reference to FIGS. 4E-4F. Asexplained herein, the user device 100 may receive the search query 230from the user 226 while (e.g., during) receiving the user input 228 fromthe user 226, or following (e.g., in response to) receiving the input228. For example, the user 226 may provide a prolonged user input 228having a time duration that is relatively longer than a momentary userinput to the user device 100 and, while continuing to provide the input228, also provide the search query 230 to the device 100 via voiceinput. Alternatively, the user 226 may provide a momentary user input228 having a relatively short time duration to the user device 100, and,after completing providing the input 228, provide the search query 230to the device 100 via voice input. In still other examples, the user 226may provide the user input 228 to the user device 100 in the form of apredetermined user gesture with respect to the selected app icon. Forexample, the user input 228 may correspond to a motion that fully orpartially encircles the app icon on the touchscreen 102.

In any case, in the example of FIGS. 3A-3B, in response to receiving theuser input 228 and search query 230 from the user 226, the user device100 generates one or more search results 234 based on the query 230. Insome examples, the user device 100 may generate the search results 234in response to (e.g., upon) receiving the search query 230. In otherexamples, in cases where the user 226 provides the search query 230 tothe user device 100 while providing a prolonged user input 228, thedevice 100 may generate the search results 234 in response to (e.g.,upon) the user 226 terminating the input 228 (e.g., upon the user 226removing a finger or stylus from the touchscreen 102 of the device 100).

In this example, aside from being responsive to the search query 230,each search result 234 also specifies a state of the native appassociated with the selected app icon (i.e., TripAdvisor). For example,to generate the search results 234, the user device 100 may perform asearch of a local storage location associated with TripAdvisor using thesearch query 230, query an API corresponding to TripAdvisor using thequery 230, or transmit the query 230 to a search system 104. In someexamples, to perform the search of the local storage location associatedwith TripAdvisor using the search query 230 and/or to query the APIcorresponding to TripAdvisor using the query 230, the user device 100(e.g., the app/query search module 220) may first launch TripAdvisor andsubsequently perform the search or query the API through (e.g., via) thelaunched TripAdvisor (e.g., by directing TripAdvisor using one or morecommands). In other examples, to transmit the search query 230 to thesearch system 104 (and, e.g., receive the search results 234 from thesystem 104), the user device 100 (e.g., the app/query search module 220)may execute the search app 214 (e.g., in the background).

As shown in FIG. 3B, upon generating the search results 234 using any ofthe techniques described above, the user device 100 may display theresults 234 at the touchscreen 102 as one or more user selectable links.In the example of FIG. 3B, the user device 100 displays the searchresults 234 as the user selectable links within a GUI 300A ofTripAdvisor that also indicates the search query 230. In other words, inthis example, the user device 100 first launches TripAdvisor, and thendisplays the search results 234 as the user selectable links within theGUI 300A of the launched TripAdvisor. In other examples (not shown), theuser device 100 may display the search results 234 as the userselectable links using another GUI (e.g., that of the web browser app210, any of the native app(s) 212, the search app 214, or another GUI).In still other examples (also not shown), the user device 100 mayforward the search results 234 for display as the user selectable linksat another computing device.

FIGS. 3C-3D depict GUI elements and user 226/user device 100interactions that are analogous to those described above with referenceto FIGS. 3A-3B. In the example of FIGS. 3C-3D, the user device 100 is asmart watch computing device that displays the search results 234 as theuser selectable links within a GUI 300B of TripAdvisor.

FIGS. 4A-4B illustrate examples in which the user device 100 provides auser prompt 400A, 400B to the user 226 and receives the search query 230from the user 226 via voice input in response to providing the prompt400A, 400B. In the example of FIGS. 4A-4B, the user prompt 400A, 400B isa visual output (e.g., a GUI element including an image of a microphone)configured to prompt the user 226 to provide the search query 230 to theuser device 100. In other examples, the user prompt 400A, 400B mayinclude any combination of a visual, audible, and/or haptic output, asdescribed herein. As shown in each of FIGS. 4A-4B, initially, the userdevice 100 receives the user input 228 from the user 226 at thetouchscreen 102, in a similar manner as described above with referenceto FIGS. 3A-3B. As also shown, upon (e.g., in response to) receiving theuser input 228, the user device 100 provides the user prompt 400A, 400Bto the user 226 (i.e., displays the GUI element) at the touchscreen 102.As further shown, upon (e.g., in response to) providing the user prompt400A, 400B to the user 226, the user device 100 receives the searchquery 230 from the user 226 via voice input.

FIGS. 4C-4D illustrate examples in which the user device 100 providesthe user prompt 400A, 400B to the user 226, receives an original searchquery 230A from the user 226 via voice input in response to providingthe prompt 400A, 400B, and generates a modified search query 230B usinga text input received from the user 226. As shown in each of FIGS. 4Cand 4D, initially, the user device 100 receives the user input 228 fromthe user 226 at the touchscreen 102, in a similar manner as describedabove with reference to FIGS. 3A-3B. As also shown, upon (e.g., inresponse to) receiving the user input 228, the user device 100 providesthe user prompt 400A, 400B to the user 226 at the touchscreen 102. Asfurther shown, upon (e.g., in response to) providing the user prompt400A, 400B to the user 226, the user device 100 receives a search query“RESTAURANTS” 230A from the user 226 via voice input. As still furthershown, upon receiving the original search query 230A, the user device100 generates a modified (e.g., revised) search query “RESTAURANTS INCHICAGO” 230B using a text input received from the user 226 using a textinput field 400C, 400D displayed to the user 226 by the device 100. Inthis example, the user device 100 receives the text input from the user226 via a virtual keyboard displayed to the user 226 at the touchscreen102. In other examples, the user device 100 may receive the text inputfrom the user 226 via a dedicated keypad of the device 100.

FIGS. 4E and 4F illustrate examples in which the user device 100receives the search query 230 from the user 226 via text input. As shownin each of FIGS. 4E and 4F, initially, the user device 100 receives theuser input 228 from the user 226 at the touchscreen 102, in a similarmanner as described above with reference to FIGS. 3A-3B. As also shown,the user device 100 further receives the search query 230 of“RESTAURANTS IN CHICAGO” from the user 226 via text input. In thisexample, the user device 100 receives the text input from the user 226using the text input field 400C, 400D displayed to the user 226 by thedevice 100. Specifically, the user device 100 receives the text inputfrom the user 226 via a virtual keyboard displayed to the user 226 atthe touchscreen 102. In other examples, the user device 100 may receivethe text input from the user 226 via a dedicated keypad included on thedevice 100.

FIGS. 5A-5D are flow diagrams that illustrate example methods 500A-500D,respectively, for performing a search at a user device 100 based on auser input 228 and a search query 230 received from a user. Withreference to FIG. 5A, in block 502A, a user device 100 may initiallyreceive a user input 228 (e.g., a finger contact and/or pressure input)from a user of the device 100 at a touchscreen 102 of the device 100. Asexplained herein, the user input 228 may select an app icon displayed atthe touchscreen 102. In block 504A, the user device 100 may optionallyprovide a user prompt (e.g., a visual, audible, and/or haptic output) tothe user. In this example, the user prompt may be configured to causethe user to provide a search query 230 to the user device 100. In anycase, in block 506A, e.g., in response to providing the user prompt, theuser device 100 may receive the search query 230 from the user. Forexample, the user device 100 may receive the search query 230 from theuser via voice or text input. In block 508A, in response to receivingthe user input 228 and search query 230, the user device 100 maygenerate one or more search results 234 based on the query 230. In thisexample, each search result 234 is both responsive to the search query230 and specifies a state of a native app associated with the app iconselected by the user input 228. As described herein, the user device 100may generate the search results 234 internally (e.g., by performing asearch within the native app using the search query 230), by querying anAPI associated with the app using the query 230 (e.g., using the app),or by transmitting the query 230 to the search system 104.

As one example, with reference to FIG. 5B, in block 502B, the userdevice 100 may determine (e.g., identify) a local storage location(e.g., memory space) included on the device 100. In this example, thelocal storage location corresponds to the native app associated with theapp icon selected by the user input 228 (e.g., the app uses the locationto store data used by the app). In block 504B, the user device 100 mayperform a search of the local storage location using the search query230 and, in block 506B, generate the search results 234 based on (e.g.,as a result of) performing the search. As another example, withreference to FIG. 5C, in block 502C, the user device 100 may determine(e.g., identify) an API that corresponds to the native app associatedwith the selected app icon. For example, the API may refer to one ormore remote servers and/or data stores used by the native app during thecourse of its operation. In block 504C, the user device 100 may querythe API using the search query 230 and, in block 506C, receive thesearch results 234 from the API in response to querying the API. Asstill another example, with reference to FIG. 5D, in block 502D, theuser device 100 may transmit the search query 230 to the search system104. In block 504D, the user device 100 may further transmit anindication of the native app associated with the selected app icon tothe search system 104. In block 506D, the user device 100 may receivethe search results 234 from the search system 104 in response totransmitting the search query 230 and the indication.

In any case, in block 510A, the user device 100 displays the searchresults 234 to the user as one or more user selectable links. In someexamples, the user device 100 may display the search results 234 as theuser selectable links at the touchscreen 102 of the device 100 (e.g.,within a GUI of the native app associated with the app icon selected bythe user input 228). In other examples, the user device 100 may forwardthe search results 234 to be displayed as the user selectable links atanother computing device other than the device 100.

FIG. 5E is a flow diagram that illustrates an example method 500E forperforming one or more actions in response to a user selecting a searchresult 234 displayed on a user device 100. As shown in FIG. 5E, in block502E, the user device 100 may initially determine (e.g., detect) thatthe user has selected one of the user selectable links displayed to theuser as described above with reference to FIG. 5A. In block 504E, inresponse to detecting the user selection, the user device 100 maydetermine whether to perform one or more of the following actions. Asone example, as shown in blocks 506E and 508E, the user device 100 maylaunch a native app referenced by the selected user selectable link(e.g., by an app access mechanism, or “AAM,” included in the link) andset the app into a state specified by the link (e.g., by the AAM). (AAMsare discussed in further detail below). As another example, as shown inblocks 510E and 512E, the user device 100 may download the native app(e.g., from a digital distribution platform using an app downloadaddress (“ADA”) also included in the selected user selectable link) andinstall the app. In this example, upon downloading and installing thenative app, the user device 100 may launch the app and set the app intothe state, in a similar manner as described above with reference toblocks 506E and 508E. As still another example, as shown in blocks 514Eand 516E, the user device 100 may launch a web browser app 210 includedon the device 100 and access a uniform resource locator (“URL”)corresponding to a state of a web-based app (e.g., using a web accessmechanism (“WAM”) also included in the selected user selectable link).In this example, the state of the web-based app may be an equivalent ofthe state of the native app described above.

The user device 100 may determine whether to perform any combination ofthe above-described actions. As one example, in the event the native appreferenced by the selected user selectable link is installed on the userdevice 100, the device 100 may launch the app and set the app into thestate. As another example, in the event the native app is not installedon the user device 100, the device 100 may download and install the app(e.g., followed by launching and setting the app into the state). Asstill another example, in the event the user device 100 lacks sufficientstorage space and/or communications network bandwidth to download and/orinstall the native app as described above, the device 100 may launch theweb browser app 210 and access the URL corresponding to the webequivalent of the state.

FIG. 6 is a functional block diagram illustrating an example environmentthat includes a user device 100 and a search system 104 that communicatevia a network 106. The network 106 through which the user device 100 andsearch system 104 communicate may include any type of network, such as alocal area network (LAN), a wide area network (WAN), and/or theInternet. As shown in FIG. 6, the search system 104 includes a searchmodule 108, a search data store 110, and a result generation module 112,which are described below.

In the example of FIG. 6, the user device 100 receives a user input 228(e.g., a finger contact and/or pressure input) from a user of the device100 at a touchscreen 102 of the device 100, as described herein. In thisexample, the user input 228 selects an app icon displayed at thetouchscreen 102. The user device 100 further receives a search query 230from the user (e.g., via voice or text input), as also described herein.In some examples, to receive the search query 230, the user device 100may provide a user prompt (e.g., a visual output, such as a GUI element,at the touchscreen 102; an audible output, such as a sound or a voiceinstruction, at a speaker element of the device 100; and/or a hapticoutput, such as a vibration, using a haptic driver of the device 100) tothe user. In these examples, the user prompt may be configured to promptthe user to provide the search query 230 to the user device 100. In anycase, in response to receiving the user input 228 and search query 230from the user, the user device 100 generates one or more search results234 based on the query 230. In this example, each search result 234 isboth responsive to the search query 230 and specifies a state (e.g., aGUI, or screen) of a native app associated with the app icon selected bythe user input 228. The user device 100 then displays the search results234 to the user (e.g., as one or more user selectable links), as furtherdescribed herein. For example, the user device 100 may display thesearch results 234 at the touchscreen 102 (e.g., within a GUI of thenative app associated with the selected app icon). Alternatively, theuser device 100 may forward the search results 234 for display atanother computing device.

In the example of FIG. 6, to generate the search results 234, the userdevice 100 interacts with the search system 104. In particular, the userdevice 100 receives the search query 230 from the user (e.g., inresponse to providing the user prompt) and transmits the query 230 tothe search system 104. In some examples, the user device 100 may alsotransmit an indication (e.g., a name) of the native app associated withthe app icon selected by the user input 228 to the search system 104.The search system 104 receives the search query 230 (and, e.g., theindication) from the user device 100 and generates the search results234 in response to receiving (e.g., based on) the query 230 (and, e.g.,the indication). Specifically, the search system 104 generates thesearch results 234 based on the search query 230 (and, e.g., theindication) and using information included in one or more app staterecords stored in the search data store 110. In this example, each appstate record may specify a state (e.g., a GUI, or screen) of a nativeapp. For example, each app state record may include one or more accessmechanisms (“AMs”) that enable a user device 100 to access the state ofthe native app (and, e.g., a web equivalent thereof) specified by therecord. The search system 104 transmits the AMs included in the appstate records to the user device 100 as the search results 234, asdescribed herein. Each app state record may also include app stateinformation (ASI) (e.g., text) and other information (e.g., an app statename/ID and an indication of a native app associated with the statespecified by the record), which the search system 104 may use toidentify the record in the search data store 110, as also describedherein. The search system 104 transmits the search results 234,including the AMs, to the user device 100. The user device 100 receivesthe search results 234 from the search system 104 and displays theresults 234 to the user, e.g., as one or more user selectable links thatinclude the AMs. In some examples, the user device 100 forwards thesearch results 234 for display as the user selectable links to anothercomputing device.

In this disclosure, an application or app may refer to computer softwarethat causes a computing device (e.g., the user device 100) to perform atask. In some examples, an app may be referred to as a “program.”Example apps include word processing apps, spreadsheet apps, messagingapps, media streaming apps, social networking apps, and games. Apps canbe executed on a variety of different computing devices, includingmobile computing devices, such as smartphones, tablets, and wearablecomputing devices (e.g., headsets and/or watches). Apps can also beexecuted on other types of computing devices having other form factors,such as laptop or desktop computers, or other consumer electronicdevices. In some examples, apps may be installed on a computing deviceprior to a user purchasing the device. In other examples, the user maydownload and install apps on the computing device after purchasing thedevice. A native app, as used herein, may refer to an app that isinstalled and executed on a user device 100. A web-based app, in turn,may refer to an app that is accessible from a user device 100 via a webbrowser app 210.

An AM, as used herein, may include any of a native app AM (“app AM,” or“AAM”), a web AM (“WAM”), and an app download address (“ADA”). As such,the user device 100 of the present disclosure may use an AM to accessthe functionality provided by a native or a web-based app. For example,a user of the user device 100 may select a user selectable link thatincludes the AM to access the functionality of the native or web-basedapp.

An AAM may be a string that references a native app and indicates one ormore operations for a user device 100 (e.g., the app) to perform. If auser of the user device 100 selects a user selectable link that includesthe AAM, the device 100 may launch the native app referenced by the AAMand (e.g., cause the app to) perform the operations indicated by theAAM. In other words, the user selecting the user selectable link maycause the user device 100 to launch the native app and set the app intoa state (e.g., in which the app displays a GUI, or screen) correspondingto the operations. The state of the native app may be referred to as an“app state.” As a result, the native app may be configured to displayone or more products, services, or vendors, to the user, e.g., via adisplay (e.g., a touchscreen 102) of the user device 100. In thismanner, the AAM may specify the state of the native app. The state, inturn, may refer to the operations indicated by the AAM and/or theoutcome of the native app performing the operations in response to theuser selecting the user selectable link including the AAM.

A WAM may include a resource identifier that references a web resource(e.g., a page of a web-based app, or website). For example, the WAM mayinclude a uniform resource locator (URL) (i.e., a web address) used withthe hypertext transfer protocol (HTTP). If a user of a user device 100selects a user selectable link that includes the WAM, the device 100 maylaunch a web browser app 210 included on the device 100 and retrieve theweb resource referenced by the resource identifier. Stated another way,if the user selects the user selectable link, the user device 100 maylaunch the web browser app 210 and access a state (e.g., a page) of aweb-based app, or website, specified by the WAM. In some examples, a WAMincluded in an app state record along with an AAM may specify a state ofa web-based app that is equivalent (e.g., analogous) to a state of anative app specified by the AAM.

An ADA may specify a location (e.g., a digital distribution platform,such as the Play Store® developed by Google Inc.) where a native app(e.g., a native app referenced by an AAM) may be downloaded. In someexamples, an app state record may include an ADA along with an AAM (and,e.g., a WAM). In these examples, the ADA may specify a location (e.g., adigital distribution platform) from which a native app referenced by theAAM may be downloaded.

In some examples, the search system 104 may transmit the search results234, including the AMs, to the user device 100 with additional data. Forexample, the search system 104 may transmit link (e.g., text and/orimage) data that the user device 100 may use to generate the userselectable links for the AMs included in the search results 234. As aresult, each user selectable link may include text and/or image datathat the user of the user device 100 may select (e.g., touch, or “clickon”). Each user selectable link may also be associated with thecorresponding one or more of the AMs included in the search results 234,such that when the user selects the link, the user device 100 launches anative or web-based app referenced by the AMs and causes the app toperform one or more operations indicated by the AMs. In some examples,the text and/or image data included in each user selectable link mayindicate the operations performed by the corresponding native orweb-based app upon selection of the link.

As described herein, the search system 104 uses data (e.g., app staterecords) included in the search data store 110 to generate searchresults 234 based on search queries 230 (and, e.g., indications ofnative apps associated with app icons selected by user inputs 228)received from the user device 100. The search data store 110 may includeone or more databases, indices (e.g., inverted indices), tables, files,or other data structures that may be used to implement the techniques ofthe present disclosure. In some examples, the search data store 110 maybe included in one or more storage devices. The search data store 110includes one or more app state records (e.g., as shown in FIG. 9A). Eachapp state record may include data related to a function of a native appand/or a state of the app resulting from the app performing thefunction. For example, each app state record may include, among othercontent, an app state name/ID, ASI, and one or more AMs. The app statename/ID may uniquely identify the app state record among other app staterecords included in the search data store 110. The ASI may describe astate into which a native app is set according to one or more AMsincluded in the app state record. The AM (e.g., an AAM, or a WAM) mayinclude data (e.g., a text/number string) that causes a user device 100to launch a native or web-based app and perform a function associatedwith the app. In some examples, the AM may include data (e.g., an ADA)that enables a user device 100 to download and install (e.g., from adigital distribution platform) a native app on a user device 100.Example app state records are shown in FIGS. 9A and 9B.

As described above, the search system 104 receives the search query 230(and, e.g., the indication of the native app associated with the appicon selected by the user input 228) from the user device 100, generatesthe search results 234 based on the query 230 (and, e.g., theindication), and transmits the results 234 to the device 100. The searchquery 230 may include text, numbers, and/or symbols (e.g., punctuation)entered into the user device 100 by the user via voice and/or textinput. In some examples, the user device 100 may receive the searchquery 230 from the user and/or transmit the query 230 to the searchsystem 104 using the search app 214 included (e.g., running in thebackground on) the device 100. For example, the search app 214 mayreceive the search query 230 from the user using any of voicerecognition software included on the user device 100, a virtual keyboarddisplayed at the touchscreen 102, and a dedicated mechanical keypad ofthe device 100, and then transmit the query 230 to the search system104.

In other examples, the user device 100 may further generate theindication of the native app associated with the selected app iconand/or transmit the indication to the search system 104 using the searchapp 214. The indication may include any of text, numbers, and/or symbols(e.g., punctuation), as well as any machine-readable (e.g., binary) dataused by the user device 100 (e.g., the search app 214) to represent thenative app associated with the selected app icon. In some examples, thesearch app 214 may transmit the indication to the search system 104along with the search query 230. In other examples, the search app 214may also receive the search results 234 from the search system 104and/or display the results 234 to the user on the device 100 as userselectable links. The search app 214 may be a native app dedicated tosearch, or a more general app, such as the web browser app 210 alsoincluded on the user device 100.

In some examples, the user device 100 may transmit additional data tothe search system 104 along with the search query 230. The search query230 and the additional data may be referred to herein as a querywrapper. The additional data may include geo-location data associatedwith the user device 100, platform data for the device 100 (e.g., a typeand/or a version of the device 100, an OS, and/or the web browser app210 of the device 100), an identity of the user (e.g., a username),partner specific data, and other data. The user device 100 may transmitthe query wrapper to the search system 104. The search system 104 mayuse the search query 230 and/or the additional data included in thequery wrapper to generate the search results 234 and transmit theresults 234 to the user device 100.

As described herein, to generate the search results 234, the searchmodule 108 may identify one or more app state records included in thesearch data store 110 based on the search query 230 and, e.g., theindication of the native app associated with the selected app icon.Initially, the search module 108 may analyze the search query 230. Thesearch module 108 may then identify one or more app state recordsincluded in the search data store 110 based on the (e.g., analyzed)search query 230. In some examples, the search module 108 may furtheridentify the app state records based on the indication. For example, thesearch module 108 may identify the app state records based on (e.g.,text) matches between terms of the search query 230 (and, e.g., theindication) and terms of information included in the records. The searchmodule 108 may then process (e.g., score) the identified app staterecords. For example, the search module 108 may determine how well theidentified app state records match the search query 230 (and, e.g., theindication). The search module 108 may then select one or more of theidentified app state records that best match the search query 230 (and,e.g., the indication). The search module 108 may transmit one or moreapp state IDs associated with the selected app state records to theresult generation module 112. The result generation module 112 mayidentify the app state records selected by the search module 108 in thesearch data store 110 using the received app state IDs. The resultgeneration module 112 may then select one or more AMs from theidentified app state records. The result generation module 112 maytransmit the selected AMs to the user device 100 as the search results234.

In some examples, the result generation module 112 may transmitadditional information along with the AMs to the user device 100. Forexample, as described herein, a set processing module 806 of the searchmodule 108 may generate result scores for the app state records fromwhich the AMs are selected (e.g., using values of metrics associatedwith persons, places, or things described in the records and/or variousfeatures of the search query 230). As such, the one or more AMs selectedfrom each app state record may be associated with a result score thatindicates a rank of the AMs relative to AMs selected from other appstate records. In these examples, the result generation module 112 maytransmit the result scores associated with the AMs to the user device100 along with the AMs. In additional examples, the result generationmodule 112 may also transmit link (e.g., text and/or image) dataassociated with the AMs to the user device 100 to be used to display theAMs to a user, as also described herein.

The search system 104 may use various sources of data to generate and/orupdate the search data store 110. For example, the search system 104 mayuse the data sources to generate and/or update one or more databases,indices, tables, files, or other data structures included in the searchdata store 110. For instance, the search system 104 may generate new appstate records and/or update existing app state records using dataretrieved from the data sources. Although not shown, in some examples,the search system 104 may include one or more modules configured togenerate the new app state records and/or update the existing app staterecords. In some examples, some or all of the data included in thesearch data store 110 (e.g., one or more app state records) may bemanually generated by a human operator.

The data sources may include a variety of different data providers. Forexample, the data sources may include data from app developers, such asapp developer websites and data feeds provided by app developers. Thedata sources may also include operators of digital distributionplatforms configured to distribute apps to user devices 100. The datasources may further include other websites, such as websites thatinclude web logs (i.e., blogs), app reviews, and/or other data relatedto apps. Additionally, the data sources may include social networkingsites, such as “FACEBOOK®” by Facebook, Inc. (e.g., Facebook posts) and“TWITTER®” by Twitter, Inc. (e.g., text from tweets). The data sourcesmay also include online databases that include data related to movies,television programs, music, and restaurants. The data sources mayfurther include other resources, which may have various types of contentand update rates.

In some examples, the search system 104 may retrieve data from the datasources, including any type of data related to native app functionalityand/or states. The search system 104 may then generate one or more appstate records based on the data and store the records in the search datastore 110. In other examples, some or all of the data included in theapp state records (e.g., ASI) may be manually generated by a humanoperator. In further examples, the data included in the app staterecords may be updated over time so that the search system 104 providesup-to-date search results 234 in response to user-specified searchqueries 230 (and, e.g., indications of native apps associated withselected app icons) received from the user device 100.

FIG. 7 shows an example search system 104. As described herein, thesearch system 104 generates search results 234 based on a search query230 (and, e.g., an indication of a native app associated with an appicon selected by a user input 228) received from the user device 100 andusing data included in the search data store 110. Specifically, thesearch module 108 identifies one or more app state records included inthe search data store 110 based on the search query 230 (and, e.g.,based on the indication). The search module 108 then transmits one ormore app state IDs 700 that identify the identified app state records tothe result generation module 112. The result generation module 112receives the app state IDs 700 from the search module 108, identifiesthe app state records in the search data store 110 using the IDs 700,and selects one or more AMs from the identified records. The resultgeneration module 112 then transmits the selected AMs to the user device100 as the search results 234 (e.g., along with result scores, linkdata, and/or other information).

FIG. 8 shows an example search module 108 and an example search datastore 110. The search module 108 of FIG. 8 includes a query analysismodule 802, a consideration set generation module (hereinafter, “setgeneration module”) 804, and a consideration set processing module(hereinafter, “set processing module”) 806. The query analysis module802 receives a search query 230 from the user device 100 (e.g., as partof a query wrapper) and analyzes the query 230 (e.g., performs any oftokenization, filtering, stemming, synonymization, and stop word removalwith respect to the query 230). The set generation module 804 identifiesone or more app state records included in the search data store 110based on the (e.g., analyzed) search query 230. In some examples, theset generation module 804 may further identify the app state recordsbased on an indication of a native app associated with an app icon thathas been selected by a user input 228 on the user device 100, which mayalso be received from the device 100 as described herein. As a specificexample, the set generation module 804 may identify the app staterecords using the search query 230 and, e.g., the indication, as one ormore inputs to Lucene® information retrieval software developed by theApache Software Foundation. The set generation module 804 may identifythe app state records based on one or more (e.g., text) matches betweenone or more terms of the search query 230 and, e.g., the indication, andone or more terms of information (e.g., app state names/IDs and/or ASI)included in the records. The identified app state records may bereferred to herein as a “consideration set.” The set processing module806 may process (e.g., score and select a subset of) the considerationset to generate one or more app state IDs 700 that identify some or allof the app state records, and transmit the IDs 700 to the resultgeneration module 112, as described above.

The information conveyed by the search results 234 may depend on themanner in which the set processing module 806 generates the resultscores for the identified app state records. For example, for eachidentified app state record, the corresponding result score may indicaterelevance of the state of the native app specified by the record to thesearch query 230, popularity of the state, and/or other properties ofthe state, depending on the one or more parameters the set processingmodule 806 uses to score the record. The set processing module 806 maygenerate the result scores for the app state records in a variety ofdifferent ways. In some examples, the set processing module 806generates a result score for an app state record based on one or morescoring features. The scoring features may be associated with the appstate record and/or the search query 230. A record scoring feature maybe based on any data associated with an app state record. For example, arecord scoring feature may be based on any data included in ASI of anapp state record. Example record scoring features may be a qualityscore, or whether an app state record includes an AAM that specifies adefault state (e.g., a main page), or a deeper state, of a native app. Aquery scoring feature may include any data associated with the searchquery 230. For example, a query scoring feature may include a number ofwords in the search query 230, popularity of the query 230, and/or anexpected frequency of the words in the query 230. A record-query scoringfeature may include any data generated based on information associatedwith both an app state record and the search query 230 that resulted inidentification of the record by the set generation module 804. Forexample, record-query scoring features may include parameters thatindicate how well terms of the search query 230 match terms of ASI of anidentified app state record. In additional examples, the set processingmodule 806 may generate a result score for an app state record based onthe indication of the native app associated with the app icon that hasbeen selected by a user input 228 on the user device 100. For example,the set processing module 806 may use a scoring feature that includesparameters that indicate how well (e.g., terms of) the indication match(e.g., terms of) information included in the app state record (e.g., anindication of a native app that is associated with the state specifiedby the record). In general, the set processing module 806 may generate aresult score for an app state record based on any combination of arecord scoring feature, a query scoring feature, a record-query scoringfeature, a scoring feature related to the indication, and/or anyadditional scoring feature not explicitly listed.

In some examples, the set processing module 806 may include one or moremachine-learned models (e.g., a supervised learning model) configured toreceive one or more scoring features. The machine-learned models maygenerate one or more result scores for one or more app state recordsbased on at least one of the record, query, record-query, andindication-based scoring features described above. For example, the setprocessing module 806 may pair the search query 230 with each app staterecord and calculate a vector of features for each (query, record) pair.The vector of features may include one or more record, query,record-query, and indication-based scoring features, as describedherein. The set processing module 806 may then input the vector offeatures into a machine-learned regression model to calculate a resultscore for the app state record. In some examples, the machine-learnedregression model may include a set of decision trees (e.g.,gradient-boosted decision trees), or may be trained by a simple form oflogistic regression. In other examples, the machine-learned taskdescribed above can be framed as a semi-supervised learning task, wherea minority of the training data is labeled with human curated resultscores and the rest of the data is used without such labels.

As described herein, the result scores associated with the app staterecords (e.g., the AMs included therein) may be used in a variety ofdifferent ways. In some examples, the result scores may be used to rank(e.g., order) the corresponding AMs within a list. In these examples, ahigher result score may indicate that a corresponding AM is morerelevant to the user (e.g., to the search query 230) than an AM having asmaller result score. In examples where the search results 234 aredisplayed to the user on the user device 100 or another computing deviceas a list of one or more user selectable links, links including AMsassociated with larger result scores may be listed closer to the top ofthe list (e.g., near the top of the screen). In these examples, linksincluding AMs having lower result scores may be located farther down thelist (e.g., off screen) and may be accessed by scrolling down the screenof the user device 100 or other device.

FIG. 9A depicts an example app state record 900A that may be included inthe search data store 110. The app state record 900A of FIG. 9A includesinformation related to (e.g., specifying) a state of a native app. Asshown in FIG. 9A, the app state record 900A includes an app statename/ID 902A that uniquely identifies the record 900A among other appstate records included in the search data store 110. As further shown,the app state record 900A includes ASI (e.g., text) 904A that describesthe state specified by the record 900A. As also shown, the app staterecord 900A includes one or more AMs (e.g., AAMs, WAMs, and/or ADAs)906A that enable a user device 100 to access the state specified by therecord 900A. As shown in FIG. 9A, in some examples, the app state record900A may also include an indication (e.g., a name) 908A of the nativeapp associated with the state specified by the record 900A. In otherexamples, the app state name/ID 902A, ASI 904A, and/or AMs 906A includedin the app state record 900A may indicate (e.g., reference) theassociated native app.

In some examples, the app state record 900A of FIG. 9A may also includeinformation that describes values of one or more metrics associated witha person, place, or thing described in the record 900A. Examples of themetrics include popularity of the place described in the app staterecord 900A and/or ratings (e.g., user ratings) of the place. Forexample, if the app state record 900A describes a song, a metricassociated with the song may be based on popularity of the song and/orratings (e.g., user ratings) of the song. The information included inthe app state record 900A may also be based on measurements associatedwith the record 900A, such as how often the record 900A is retrievedduring a search and how often user selectable links for the AMs 906A ofthe record 900A are selected by a user. The information included in theapp state record 900A may also indicate whether the record 900A includesan AAM for a default state, or a deeper state, of the native appassociated with the record 900A.

FIG. 9B illustrates a specific example of an app state record 900B thatspecifies a state of TripAdvisor. The state specified by the app staterecord 900B corresponds to an entry in TripAdvisor for the restaurant“Weber Grill” located in Chicago, Ill. As shown in FIG. 9B, the appstate record 900B includes an app state name/ID “TripAdvisor—Weber GrillRestaurant, Chicago, Ill.” 902B that uniquely identifies the record 900Bamong other app state records included in the search data store 110. Inother examples, the app state name/ID 902B may be a numeric value, orhave another (e.g., machine-readable) representation. As further shown,the app state record 900B also includes ASI 904B that describes thestate specified by the record 900B, and which may be used to identifythe record 900B within the search data store 110. For example, asdescribed herein, the search system 104 may identify the app staterecord 900B within the search data store 110 based on (e.g., text)matches between terms of a search query 230 received from the userdevice 100 and terms of the ASI 904B. In this example, the ASI 904Bdescribes a restaurant category, a description, user reviews, and/or anyother information related to the restaurant associated with the statespecified by the app state record 900B. In some examples, the ASI 904Bmay also describe one or more functions provided by the state, such as,e.g., “make a restaurant reservation,” “read user reviews,” and “write auser review.” As also shown, the app state record 900B further includesone or more AMs (e.g., AAMs, WAMs, and/or ADAs) 906B that enable a userdevice 100 to access the state specified by the record 900B.

In the example of FIG. 9B, the app state record 900B also includes anindication 908B of the native app (i.e., TripAdvisor) associated withthe state specified by the record 900B, which may also be used toidentify the record 900B within the search data store 110. For instance,as described herein, the search system 104 may receive an indication ofa native app associated with an app icon that has been selected by auser input 228 from the user device 100. In some examples, the searchsystem 104 may identify the app state record 900B based on (e.g., text)matches between the received indication and the indication 908B includedin the record 900B. In other examples, the app state record 900B may notexplicitly (e.g., separately) indicate the native app associated withthe state specified by the record 900B (e.g., the record 900B may notinclude the indication 908B). In these examples, the search system 104may identify the app state record 900B based on (e.g., text) matchesbetween the received indication and any of the app state name/ID 902B,ASI 904B, and/or AMs 906B that may reference the native app.

FIG. 10 is a flow diagram that illustrates an example method 1000 forperforming a search for app state records 900A included in the searchdata store 110 using a search query 230 and, e.g., an indication of anative app, received from a user device 100. As shown in FIG. 10, inblock 1002, the search system 104 may initially receive a search query230 specified by a user from a user device 100 (e.g., as part of a querywrapper). As described herein, the user device 100 may receive thesearch query 230 from the user (e.g., via voice or text input) andtransmit the query 230 to the search system 104. In block 1004, thesearch system 104 (e.g., the query analysis module 802) may optionallyperform an analysis of the search query 230 (e.g., perform any oftokenization, filtering, stemming, synonym ization, and stop wordremoval with respect to the query 230). In some examples, the searchsystem 104 may also receive other information from the user device 100(e.g., as part of the query wrapper, or separately), such as informationassociated with the user and/or geo-location, platform, and IP addressinformation associated with the device 100. As one example, in block1006, the search system 104 may receive an indication of a native appassociated with an app icon that has been selected by a user input 228on the user device 100 from the device 100, as also described herein.

In block 1008, the search system 104 (e.g., the set generation module804) may identify a consideration set of one or more app state records900A included in the search data store 110 based on the (e.g., analyzed)search query 230 and, e.g., the indication of the native app, receivedfrom the user device 100. As described herein, each of the identifiedapp state records 900A may specify a state of a native app. As alsodescribed herein, the search system 104 may identify the app staterecords 900A based on matches between the search query 230 and, e.g.,the indication, and information (e.g., app state names/IDs 902A, ASI904A, AMs 906A, and/or indications 908A of associated native apps)included in the records 900A.

In blocks 1010-1012, the search system 104 (e.g., the set processingmodule 806) may optionally process the consideration set of the appstate records 900A. Specifically, in block 1010, the search system 104may generate one or more result scores for the app state records 900Aincluded in the consideration set. For example, the search system 104may generate a result score for each of the app state records 900A.Subsequently, in block 1012, the search system 104 may select one ormore (e.g., a subset of the) app state records 900A from theconsideration set based on the one or more result scores associated withthe selected records 900A. For example, the search system 104 may selectone or more app state records 900A included in the consideration sethaving the highest (e.g., largest) one or more result scores.

In any case, in block 1014, the search system 104 (e.g., the resultgeneration module 112) may select one or more AMs from the (e.g.,selected) app state records 900A of the consideration set. For example,the search system 104 may select one or more AAMs, ADAs, and/or WAMsfrom each (e.g., selected) app state record 900A. In some examples, thesearch system 104 may also select other information from the (e.g.,selected) app state records 900A, such as result scores and/or link dataassociated with the records 900A. In block 1016, the search system 104(e.g., the result generation module 112) may generate one or more searchresults 234 that include the selected AMs. For example, the searchsystem 104 may generate the search results 234 such that each result 234includes one or more of the AMs selected from the (e.g., selected) appstate records 900A of the consideration set. Lastly, in block 1018, thesearch system 104 (e.g., the result generation module 112) may transmitthe search results 234, including the selected AMs and any otherinformation, to the user device 100 that provided the search query 230and, e.g., the indication of the native app, to the system 104.

The modules and data stores included in the user device 100 and searchsystem 104 represent features that may be included in these devices andsystems as they are described in the present disclosure. For example,the processing unit(s) 200, memory component(s) 202, I/O component(s)204, interconnect component(s) 206, and the various contents thereof mayrepresent features included in the user device 100. Similarly, thesearch module 108, search data store 110, result generation module 112,and the various contents thereof may represent features included in thesearch system 104. The modules and data stores described herein may beembodied by electronic hardware, software, firmware, and/or anycombination thereof. Depiction of different features as separate modulesand data stores does not necessarily imply whether the modules and datastores are embodied by common or separate electronic hardware, software,and/or firmware components. As such, in some implementations, thefeatures associated with the one or more modules and data storesdepicted herein may be realized by common or separate electronichardware, software, and/or firmware components.

The modules and data stores may be embodied by electronic hardware,software, and/or firmware components, including one or more processingunits, memory components, I/O components, and interconnect components.The interconnect components may be configured to provide communicationbetween the processing units, memory components, and/or I/O components,including the transceivers. For example, the interconnect components mayinclude one or more buses configured to transfer data between electroniccomponents. The interconnect components may also include controlcircuits (e.g., a memory controller and/or an I/O controller) configuredto control communication between electronic components.

The processing units may include one or more central processing units(CPUs), graphics processing units (GPUs), digital signal processingunits (DSPs), or other processing units. The processing units may beconfigured to communicate with the memory components and I/O components.For example, the processing units may be configured to communicate withthe memory components and I/O components via the interconnectcomponents.

A memory component, or memory, may include any volatile or non-volatilemedia. For example, the memory may include electrical media, magneticmedia, and/or optical media, such as a random access memory (RAM),read-only memory (ROM), non-volatile RAM (NVRAM), electrically-erasableprogrammable ROM (EEPROM), Flash memory, hard disk drives (HDDs), solidstate drives (SSDs), magnetic tape drives, optical storage technology(e.g., compact disc, digital versatile disc, and/or Blu-ray disc), orany other memory components.

The memory components may include (e.g., store) the data describedherein. For example, the memory components may include the data includedin the record(s) 900A of the search data store 110 and/or other data.The memory components may also include instructions that may be executedby the processing units. For example, the memory components may includecomputer-readable instructions that, when executed by the processingunits, cause the units to perform the various functions attributed tothe modules and data stores described herein.

The I/O components may refer to electronic hardware, software, and/orfirmware providing communication with a variety of different devices.For example, the I/O components may provide communication between otherdevices and the processing units and memory components. In someexamples, the I/O components may be configured to communicate with acomputer network. For example, the I/O components may be configured toexchange data over a computer network using a variety of differentphysical connections, wireless connections, and protocols. The I/Ocomponents may include network interface components (e.g., a networkinterface controller), repeaters, network bridges, network switches,routers, and firewalls. In some examples, the I/O components may includehardware, software, and/or firmware configured to communicate withvarious human interface devices, including (e.g., touchscreen-enabled)display screens, keyboards, pointer devices (e.g., a mouse), (e.g.,capacitive, resistive, and/or other) touchscreens, speakers, andmicrophones. In some examples, the I/O components may include hardware,software, and/or firmware configured to communicate with additionaldevices, such as external memory (e.g., external HDDs).

In some implementations, the user device 100 and/or search system 104may be a system of one or more computing devices (e.g., a computersearch system) configured to implement the techniques described herein.Put another way, the features attributed to the modules and data storesdescribed herein may be implemented by one or more computing devices.Each computing device may include any combination of electronichardware, software, and/or firmware described above. For example, eachcomputing device may include any combination of the processing units,memory components, I/O components, and interconnect components describedabove. The computing devices may also include various human interfacedevices, including display screens, keyboards, pointing devices (e.g., amouse), touchscreens, speakers, and microphones. The computing devicesmay also be configured to communicate with additional devices, such asexternal memory (e.g., external HDDs).

The computing devices of the user device 100 and/or search system 104may be configured to communicate with the network 106. The computingdevices may also be configured to communicate with one another via acomputer network. In some examples, the computing devices of the searchsystem 104 may include one or more server computing devices configuredto communicate with the user device 100 (e.g., receive search queries230 and transmit search results 234), gather data from data sources,index the data, store the data, and store other documents or media. Insome examples, the computing devices may reside within one or moremachines at a single geographic location. In other examples, thecomputing devices may be distributed across a number of geographiclocations.

The foregoing description is merely illustrative in nature and is in noway intended to limit the disclosure, its application, or uses. Thebroad teachings of the disclosure can be implemented in a variety offorms. Therefore, while this disclosure includes particular examples,the true scope of the disclosure should not be so limited since othermodifications will become apparent upon a study of the drawings, thespecification, and the following claims. It should be understood thatone or more steps within a method may be executed in different order (orconcurrently) without altering the principles of the present disclosure.Further, although each of the embodiments is described above as havingcertain features, any one or more of those features described withrespect to any embodiment of the disclosure can be implemented in and/orcombined with features of any of the other embodiments, even if thatcombination is not explicitly described. In other words, the describedembodiments are not mutually exclusive, and permutations of one or moreembodiments with one another remain within the scope of this disclosure.

Unless explicitly described as being “direct,” when a relationshipbetween first and second elements is described in the above disclosure,that relationship encompasses a direct relationship where no otherintervening elements are present between the first and second elements,and also an indirect relationship where one or more intervening elementsare present (either spatially or functionally) between the first andsecond elements. As used herein, the phrase at least one of A, B, and Cshould be construed to mean a logical (A OR B OR C), using anon-exclusive logical OR, and should not be construed to mean at leastone of A, at least one of B, and at least one of C.”

In this application, including the definitions below, the term “module”or the term “controller” may be replaced with the term “circuit.” Theterm “module” may refer to, be part of, or include processor hardware(shared, dedicated, or group) that executes code and memory hardware(shared, dedicated, or group) that stores code executed by the processorhardware.

The module may include one or more interface circuits. In some examples,the interface circuits may include wired or wireless interfaces that areconnected to a local area network (LAN), the Internet, a wide areanetwork (WAN), or combinations thereof. The functionality of any givenmodule of the present disclosure may be distributed among multiplemodules that are connected via interface circuits. For example, multiplemodules may allow load balancing. In a further example, a server (alsoknown as remote, or cloud) module may accomplish some functionality onbehalf of a client module.

The term code, as used above, may include software, firmware, and/ormicrocode, and may refer to programs, routines, functions, classes, datastructures, and/or objects. Shared processor hardware encompasses asingle microprocessor that executes some or all code from multiplemodules. Group processor hardware encompasses a microprocessor that, incombination with additional microprocessors, executes some or all codefrom one or more modules. References to multiple microprocessorsencompass multiple microprocessors on discrete dies, multiplemicroprocessors on a single die, multiple cores of a singlemicroprocessor, multiple threads of a single microprocessor, or acombination of the above.

Shared memory hardware encompasses a single memory device that storessome or all code from multiple modules. Group memory hardwareencompasses a memory device that, in combination with other memorydevices, stores some or all code from one or more modules.

The term memory hardware is a subset of the term computer-readablemedium. The term computer-readable medium, as used herein, does notencompass transitory electrical or electromagnetic signals propagatingthrough a medium (such as on a carrier wave); the term computer-readablemedium is therefore considered tangible and non-transitory. Non-limitingexamples of a non-transitory computer-readable medium are nonvolatilememory devices (such as a flash memory device, an erasable programmableread-only memory device, or a mask read-only memory device), volatilememory devices (such as a static random access memory device or adynamic random access memory device), magnetic storage media (such as ananalog or digital magnetic tape or a hard disk drive), and opticalstorage media (such as a CD, a DVD, or a Blu-ray Disc).

The apparatuses and methods described in this application may bepartially or fully implemented by a special purpose computer created byconfiguring a general purpose computer to execute one or more particularfunctions embodied in computer programs. The functional blocks andflowchart elements described above serve as software specifications,which can be translated into the computer programs by the routine workof a skilled technician or programmer.

The computer programs include processor-executable instructions that arestored on at least one non-transitory computer-readable medium. Thecomputer programs may also include or rely on stored data. The computerprograms may encompass a basic input/output system (BIOS) that interactswith hardware of the special purpose computer, device drivers thatinteract with particular devices of the special purpose computer, one ormore operating systems, user applications, background services,background applications, etc.

The computer programs may include: (i) descriptive text to be parsed,such as HTML (hypertext markup language) or XML (extensible markuplanguage), (ii) assembly code, (iii) object code generated from sourcecode by a compiler, (iv) source code for execution by an interpreter,(v) source code for compilation and execution by a just-in-timecompiler, etc. As examples only, source code may be written using syntaxfrom languages including C, C++, C#, Objective-C, Swift, Haskell, Go,SQL, R, Lisp, Java®, Fortran, Perl, Pascal, Curl, OCaml, Javascript®,HTML5 (Hypertext Markup Language 5th revision), Ada, ASP (Active ServerPages), PHP (PHP: Hypertext Preprocessor), Scala, Eiffel, Smalltalk,Erlang, Ruby, Flash®, Visual Basic®, Lua, MATLAB, SIMULINK, and Python®.

None of the elements recited in the claims are intended to be ameans-plus-function element within the meaning of 35 U.S.C. §112(f)unless an element is expressly recited using the phrase “means for” or,in the case of a method claim, using the phrases “operation for” or“step for.”

1. A method comprising: receiving, at a touchscreen of a user device, a user input from a user of the user device, the user input selecting an application (app) icon displayed at the touchscreen; receiving, at the user device, a search query from the user; in response to receiving the user input and the search query, generating, using the user device, search results based on the search query, each search result specifying a state of a native app associated with the app icon; and displaying, using the user device, the search results to the user.
 2. The method of claim 1, wherein the user input comprises one or more of a finger contact input and a pressure input with respect to the touchscreen.
 3. The method of claim 1, wherein the user input comprises a momentary user input.
 4. The method of claim 1, wherein the user input comprises a prolonged user input having a time duration that is longer than a momentary user input.
 5. The method of claim 1, wherein the user input comprises a predetermined user gesture with respect to the touchscreen.
 6. The method of claim 1, wherein receiving the user input and the search query from the user comprises receiving the search query while receiving the user input.
 7. The method of claim 1, wherein receiving the user input and the search query from the user comprises receiving the search query following receiving the user input.
 8. The method of claim 1, wherein receiving the search query from the user comprises receiving the search query via voice input.
 9. The method of claim 1, wherein receiving the search query from the user comprises receiving the search query via text input.
 10. The method of claim 1, wherein receiving the search query from the user comprises: providing, using the user device, a user prompt to the user; and in response to providing the user prompt, receiving the search query from the user.
 11. The method of claim 10, wherein providing the user prompt to the user comprises providing one or more of the following to the user: a visual output at the touchscreen; a sound output; a voice command output; and a vibration output.
 12. The method of claim 1, wherein generating the search results in response to receiving the user input and the search query comprises: determining, using the user device, a storage location included on the user device and corresponding to the native app associated with the app icon; performing, using the user device, a search of the storage location using the search query; and generating, using the user device, the search results based on performing the search.
 13. The method of claim 1, wherein generating the search results in response to receiving the user input and the search query comprises: determining, using the user device, an app programming interface (API) corresponding to the native app associated with the app icon; querying, using the user device, the API using the search query; and receiving, at the user device, the search results from the API in response to querying the API.
 14. The method of claim 1, wherein generating the search results in response to receiving the user input and the search query comprises: transmitting, using the user device, the search query to a search system configured to generate search results in response to a received search query; and receiving, at the user device, the search results from the search system in response to transmitting the search query.
 15. The method of claim 14, further comprising transmitting, using the user device, an indication of the native app associated with the app icon to the search system, wherein receiving the search results from the search system comprises receiving the search results in response to transmitting the indication.
 16. The method of claim 1, wherein generating the search results in response to receiving the user input and the search query comprises: launching, using the user device, the native app associated with the app icon; and providing, using the user device, one or more commands to the launched native app, the one or more commands configured to cause the native app to generate the search results.
 17. The method of claim 1, wherein the search results include one or more app access mechanisms (AAMs), wherein each AAM references the native app associated with the app icon and indicates one or more operations for the native app to perform, and wherein the native app performing the one or more operations sets the native app into one of the one or more states within the native app.
 18. The method of claim 1, wherein displaying the search results to the user comprises forwarding the search results for display as one or more user selectable links to a computing device other than the user device.
 19. The method of claim 1, wherein displaying the search results to the user comprises: launching, using the user device, the native app associated with the app icon; and displaying, using a graphical user interface (GUI) of the launched native app, the search results to the user as one or more user selectable links.
 20. A computing device comprising: a touchscreen configured to display an application (app) icon and receive a user input from a user of the computing device; an input/output component configured to receive a search query from the user; one or more memory components configured to store computer-readable instructions; and one or more processing units configured to execute the computer-readable instructions, wherein the computer-readable instructions, when executed by the one or more processing units, cause the one or more processing units to: receive the user input from the user at the touchscreen, the user input selecting the app icon displayed at the touchscreen; receive the search query from the user using the input/output component; in response to receiving the user input and the search query, generate one or more search results based on the search query, each search result specifying a state of a native app associated with the app icon; and display the one or more search results to the user. 